<html>
<head><meta charset="utf-8"><title>Mod macro hygiene · general · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/122651-general/index.html">general</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/122651-general/topic/Mod.20macro.20hygiene.html">Mod macro hygiene</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="240684229"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/122651-general/topic/Mod%20macro%20hygiene/near/240684229" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> CraftSpider <a href="https://rust-lang.github.io/zulip_archive/stream/122651-general/topic/Mod.20macro.20hygiene.html#240684229">(May 29 2021 at 05:13)</a>:</h4>
<p>Have there been any updates to how <code>#[macro] mod foo;</code> should be handled since 2018, the last time it was mentioned in the <code>proc_macro_hygiene</code> tracking issue? Inner attributes seem to have even more issues, either resolution for this situation would at least make the use-case feasible. Expand-in-place would be easy, but the WYSIWYG way would also work as the macro could just parse and include the file itself (ugly, but would work).</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>